fix(gemini-enterprise): clean up dead variables, redundant CLI definitions, and prompt wording - #206

Description

This pull request addresses several minor non-destructive bug fixes and UX improvements in the Gemini Enterprise blueprint and gem4gov CLI:

• Fixes [Bug] gem4gov-cli: license command group is defined twice in gem4gov.py #110: Removes the duplicate license command group definition from gem4gov.py.
• Fixes [Bug] gem4gov onboard data-store prompt says "already created and loaded with data" but loading is not required (or checked) — misleads operators into importing before onboarding #144: Clarifies the onboard datastore prompt in gem4gov.py to remove 'loaded with data' since pre-loading data is not a prerequisite to connecting a datastore.
• Fixes [Bug] gemini-stage-1: terraform.tfvars.sample still sets gemini_config_id, which the stage no longer declares — "Value for undeclared variable" on every plan and apply #175: Removes the deprecated gemini_config_id variable from gemini-stage-1/terraform.tfvars.sample.
• Fixes [Bug] gemini-stage-0: kms_project_id and us_keyring_name are declared but referenced nowhere, and us_keyring_name's description promises a keyring the stage never creates #176: Removes dead variables kms_project_id and us_keyring_name from gemini-stage-0/variables.tf.

Fixes #110
Fixes #144
Fixes #175
Fixes #176

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Deployment & Compliance Impact

• Applicable Regimes:
  • US Region Restricted (e.g., Access Policy constraint)
  • FedRAMP Moderate
  • FedRAMP High
  • DoD IL4
  • DoD IL5
  • General / All
• NIST 800-53r5 Controls: N/A

Checklist

Code Quality & Reusability

• My code adheres to the Maximize Reusability principle. I have not redefined common elements and have reused existing base configurations and modules where possible.
• I have checked that no existing module or configuration in modules/ or fast/ can be leveraged for this change.
• My code follows the established naming conventions outlined in documentation/naming-convention.md.

Documentation

• I have updated the README.md of the modified module or blueprint.
• I have added/updated documentation for inputs (variables) and outputs.

Security

• My change adheres to GCP security best practices and the principle of least privilege.
• I have ensured compliance with the targeted regime (FedRAMP Moderate, FedRAMP High, IL5, etc.).

Testing

• I have tested my changes locally.
• I have included details of my testing in this PR.

Testing Performed

• Verified CLI command groups and prompt text in gem4gov.py.
• Verified Terraform variable definitions in gemini-stage-0 and gemini-stage-1.